Skip to content

cmd/mcp_test: use t.Setenv to prevent env var leak across tests#3688

Open
Elvand-Lie wants to merge 1 commit intoknative:mainfrom
Elvand-Lie:fix/mcp-test-env-leak
Open

cmd/mcp_test: use t.Setenv to prevent env var leak across tests#3688
Elvand-Lie wants to merge 1 commit intoknative:mainfrom
Elvand-Lie:fix/mcp-test-env-leak

Conversation

@Elvand-Lie
Copy link
Copy Markdown

@Elvand-Lie Elvand-Lie commented May 9, 2026

TestMCP_StartWriteable sets FUNC_ENABLE_MCP_WRITE via os.Setenv but never cleans it up. Since Go runs all tests in a package within the same process, this leaked env var persists for subsequent tests.

Replace os.Setenv with t.Setenv, which automatically restores the original value when the test finishes. Remove the now-unused os import.

Changes

  • Replace os.Setenv with t.Setenv in TestMCP_StartWriteable to auto-restore the env var after the test
  • Remove unused "os" import from cmd/mcp_test.go

Fixes #3686

Release Note

NONE

TestMCP_StartWriteable sets FUNC_ENABLE_MCP_WRITE via os.Setenv but never cleans it up. Since Go runs all tests in a package within the same process, this leaked env var persists for subsequent tests.

Replace os.Setenv with t.Setenv, which automatically restores the original value when the test finishes. Remove the now-unused os import.

Fixes knative#3686

Signed-off-by: elvandlie@gmail.com <elvandlie@gmail.com>
@knative-prow
Copy link
Copy Markdown

knative-prow Bot commented May 9, 2026

@Elvand-Lie: The label(s) kind/<kind> cannot be applied, because the repository doesn't have them.

Details

In response to this:

TestMCP_StartWriteable sets FUNC_ENABLE_MCP_WRITE via os.Setenv but never cleans it up. Since Go runs all tests in a package within the same process, this leaked env var persists for subsequent tests.

Replace os.Setenv with t.Setenv, which automatically restores the original value when the test finishes. Remove the now-unused os import.

Fixes #3686

Changes

/kind

Fixes #

Release Note


Docs


Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@knative-prow
Copy link
Copy Markdown

knative-prow Bot commented May 9, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Elvand-Lie
Once this PR has been reviewed and has the lgtm label, please assign dsimansk for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@linux-foundation-easycla
Copy link
Copy Markdown

linux-foundation-easycla Bot commented May 9, 2026

CLA Signed
The committers listed above are authorized under a signed CLA.

@knative-prow knative-prow Bot requested review from dsimansk and jrangelramos May 9, 2026 14:14
@knative-prow knative-prow Bot added the size/XS 🤖 PR changes 0-9 lines, ignoring generated files. label May 9, 2026
@knative-prow
Copy link
Copy Markdown

knative-prow Bot commented May 9, 2026

Welcome @Elvand-Lie! It looks like this is your first PR to knative/func 🎉

@knative-prow
Copy link
Copy Markdown

knative-prow Bot commented May 9, 2026

Hi @Elvand-Lie. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@knative-prow knative-prow Bot added the needs-ok-to-test 🤖 Needs an org member to approve testing label May 9, 2026
@Elvand-Lie
Copy link
Copy Markdown
Author

/kind bug

@knative-prow knative-prow Bot added the kind/bug Bugs label May 9, 2026
@knative-prow
Copy link
Copy Markdown

knative-prow Bot commented May 9, 2026

@Elvand-Lie: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/ok-to-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/bug Bugs needs-ok-to-test 🤖 Needs an org member to approve testing size/XS 🤖 PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cmd/mcp_test: TestMCP_StartWriteable leaks FUNC_ENABLE_MCP_WRITE environment variable

1 participant